Release v0.79.3#21
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Thurgood-AI
approved these changes
Jul 11, 2026
Thurgood-AI
left a comment
There was a problem hiding this comment.
Approved. Release metadata is consistent across all publishable workspaces, internal dependency ranges, root lockfile, example locks, npm shrinkwrap, and changelogs.
Verification:
check:shrinkwrappasses locally- All publishable workspace versions resolve to 0.79.3
- Full CI build/check/test passes
- Vercel and contributor gates pass
Per the PR note, merge with a regular merge commit so the tagged release commit remains in main's history.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release prepared by
scripts/release.mjs patch(version bump, changelogs, regenerated artifacts, full build + checks + tests — all green locally withPI_NO_LOCAL_LLM=1).Submitted as a PR because the
mainruleset now blocks the Release workflow's direct push (GH013: Changes must be made through a pull request— the workflow has been broken since the rule was added; v0.79.2 predates it). Once this merges, thev0.79.3tag gets pushed to trigger the npm publish workflow.Merge note: please use a regular merge commit (not squash) so the tagged release commit lands in main's history. The post-merge "Release" workflow run on main will fail at its push step for the same ruleset reason — that red X is expected noise until the bot gets a bypass.
Ships: CD-1284 (streamed vault downloads + native
vault_read_text) — first release since Jun 23.🤖 Generated with Claude Code